home *** CD-ROM | disk | FTP | other *** search
-
-
-
- EEEELLLLFFFF____GGGGEEEETTTTIIIIDDDDEEEENNNNTTTT((((3333EEEE)))) EEEELLLLFFFF____GGGGEEEETTTTIIIIDDDDEEEENNNNTTTT((((3333EEEE))))
-
-
-
- NNNNAAAAMMMMEEEE
- _eeee_llll_ffff______gggg_eeee_tttt_iiii_dddd_eeee_nnnn_tttt - retrieve file identification data
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- _cccc_cccc [_f_l_a_g ...] _f_i_l_e ... _----_llll_eeee_llll_ffff [_l_i_b_r_a_r_y ...]
-
- _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_llll_iiii_bbbb_eeee_llll_ffff_...._hhhh_>>>>
- _cccc_hhhh_aaaa_rrrr _****_eeee_llll_ffff______gggg_eeee_tttt_iiii_dddd_eeee_nnnn_tttt_((((_EEEE_llll_ffff _****_eeee_llll_ffff_,,,, _ssss_iiii_zzzz_eeee______tttt _****_pppp_tttt_rrrr_))))_;;;;
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- As _eeee_llll_ffff(3E) explains, ELF provides a framework for various classes of
- files, where basic objects may have 32 bits, 64 bits, etc. To
- accommodate these differences, without forcing the larger sizes on
- smaller machines, the initial bytes in an ELF file hold identification
- information common to all file classes. Every ELF header's _eeee______iiii_dddd_eeee_nnnn_tttt has
- _EEEE_IIII______NNNN_IIII_DDDD_EEEE_NNNN_TTTT bytes with the following interpretation.
-
- _eeee______iiii_dddd_eeee_nnnn_tttt Index Value Purpose
- __________________________________________________
- _EEEE_IIII______MMMM_AAAA_GGGG_0000 _EEEE_LLLL_FFFF_MMMM_AAAA_GGGG_0000
- _EEEE_IIII______MMMM_AAAA_GGGG_1111 _EEEE_LLLL_FFFF_MMMM_AAAA_GGGG_1111
- _EEEE_IIII______MMMM_AAAA_GGGG_2222 _EEEE_LLLL_FFFF_MMMM_AAAA_GGGG_2222
- _EEEE_IIII______MMMM_AAAA_GGGG_3333 _EEEE_LLLL_FFFF_MMMM_AAAA_GGGG_3333 File identification
-
- __________________________________________________
- _EEEE_LLLL_FFFF_CCCC_LLLL_AAAA_SSSS_SSSS_NNNN_OOOO_NNNN_EEEE
- _EEEE_LLLL_FFFF_CCCC_LLLL_AAAA_SSSS_SSSS_3333_2222
- _EEEE_IIII______CCCC_LLLL_AAAA_SSSS_SSSS _EEEE_LLLL_FFFF_CCCC_LLLL_AAAA_SSSS_SSSS_6666_4444 File class
-
- __________________________________________________
- _EEEE_LLLL_FFFF_DDDD_AAAA_TTTT_AAAA_NNNN_OOOO_NNNN_EEEE
- _EEEE_LLLL_FFFF_DDDD_AAAA_TTTT_AAAA_2222_LLLL_SSSS_BBBB
- _EEEE_IIII______DDDD_AAAA_TTTT_AAAA _EEEE_LLLL_FFFF_DDDD_AAAA_TTTT_AAAA_2222_MMMM_SSSS_BBBB Data encoding
-
- __________________________________________________
- _EEEE_IIII______VVVV_EEEE_RRRR_SSSS_IIII_OOOO_NNNN _EEEE_VVVV______CCCC_UUUU_RRRR_RRRR_EEEE_NNNN_TTTT File version
- __________________________________________________
- _7777_----_1111_5555 _0000 Unused, set to zero
- __________________________________________________
- |||||||||||||||||||
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- |||||||||||||||||||
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Other kinds of files [see _eeee_llll_ffff______kkkk_iiii_nnnn_dddd(3E)] also may have identification
- data, though they would not conform to _eeee______iiii_dddd_eeee_nnnn_tttt.
-
- _eeee_llll_ffff______gggg_eeee_tttt_iiii_dddd_eeee_nnnn_tttt returns a pointer to the file's ``initial bytes.'' If the
- library recognizes the file, a conversion from the file image to the
- memory image may occur. In any case, the identification bytes are
- guaranteed not to have been modified, though the size of the unmodified
- area depends on the file type. If _p_t_r is non-null, the library stores
- the number of identification bytes in the location to which _p_t_r points.
- If no data are present, _e_l_f is null, or an error occurs, the return value
- is a null pointer, with zero optionally stored through _p_t_r.
-
-
-
-
-
- PPPPaaaaggggeeee 1111
-
-
-
-
-
-
- EEEELLLLFFFF____GGGGEEEETTTTIIIIDDDDEEEENNNNTTTT((((3333EEEE)))) EEEELLLLFFFF____GGGGEEEETTTTIIIIDDDDEEEENNNNTTTT((((3333EEEE))))
-
-
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- _eeee_llll_ffff(3E), _eeee_llll_ffff______bbbb_eeee_gggg_iiii_nnnn(3E), _eeee_llll_ffff______gggg_eeee_tttt_eeee_hhhh_dddd_rrrr(3E), _eeee_llll_ffff______kkkk_iiii_nnnn_dddd(3E), _eeee_llll_ffff______rrrr_aaaa_wwww_ffff_iiii_llll_eeee(3E).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PPPPaaaaggggeeee 2222
-
-
-
-